Terminal apparatus and method

ABSTRACT

A terminal apparatus for communicating with a base station apparatus, the terminal apparatus including: a receiver configured to receive, from the base station apparatus, an RRC message including an EHC configuration; and a processing unit. The processing unit configures an EHC protocol in accordance with the EHC configuration, and adds a context identifier to data in processing of the EHC protocol, and indicates, in a case that the context identifier is a particular value, that an Ethernet header of the data is uncompressed.

TECHNICAL FIELD

The present invention relates to a terminal apparatus and a method.

This application claims priority based on JP 2019-147899 filed on Aug.9, 2019, the contents of which are incorporated herein by reference.

BACKGROUND ART

A radio access method and a radio network for cellular mobilecommunications (which will hereinafter be referred to as “Long TermEvolution (LTE; trade name)” or “Evolved Universal Terrestrial RadioAccess (EUTRA)”) and a core network (which will be referred to as“Evolved Packet Core (EPC)”) have been studied by the 3rd GenerationPartnership Project (3GPP). EUTRA is also referred to as E-UTRA.

Furthermore, as a radio access method and a radio network technology fora 5th generation cellular system, technical studies and standardizationof LTE-Advanced Pro which is an enhanced technology of LTE and New Radiotechnology (NR) which is a new radio access technology have beenconducted by the 3GPP (NPL 1). Furthermore, 5 Generation Core Network(5GC), which is a core network for the 5th generation cellular system,has also been studied (NPL 2).

Also, as a standard for local area networks, Ethernet (trade name) isstandardized by the Institute of Electrical and Electronics Engineers(IEEE) 802 Committee.

CITATION LIST Non Patent Literature

-   NPL 1: 3GPP RP-170855, “Work Item on New Radio (NR) Access    Technology”-   NPL 2: 3GPP TS 23.501 v15.3.0, “System Architecture for the 5G    System; Stage 2”-   NPL 3: 3GPP TS 36.300 v15.3.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA) and Evolved Universal Terrestrial Radio Access    Network (E-UTRAN); Overall description; Stage 2”-   NPL 4: 3GPP TS 36.331 v15.4.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA); Radio Resource Control (RRC); Protocol    specifications”-   NPL 5: 3GPP TS 36.323 v15.3.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA); Packet Data Convergence Protocol (PDCP)    specification”-   NPL 6: 3GPP TS 36.322 v15.3.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA); Radio Link Control (RLC) protocol specification”-   NPL 7: 3GPP TS 36.321 v15.3.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA); Medium Access Control (MAC) protocol specification”-   NPL 8: 3GPP TS 37.340v 15.3.0, “Evolved Universal Terrestrial Radio    Access (E-UTRA) and NR; Multi-Connectivity; Stage 2”-   NPL 9: 3GPP TS 38.300v 15.3.0, “NR; NR and NG-RAN Overall    description; Stage 2”-   NPL 10: 3GPP TS 38.331 v15.4.0, “NR; Radio Resource Control (RRC);    Protocol specifications”-   NPL 11: 3GPP TS 38.323 v15.3.0, “NR; Packet Data Convergence    Protocol (PDCP) specification”-   NPL 12: 3GPP TS 38.322 v15.3.0, “NR; Radio Link Control (RLC)    protocol specification”-   NPL 13: 3GPP TS 38.321 v15.3.0, “NR; Medium Access Control (MAC)    protocol specification”-   NPL 14: 3GPP TS 23.401 v15.0.0, “General Packet Radio Service (GPRS)    enhancements for Evolved Universal Terrestrial Radio Access Network    (E-UTRAN) access”-   NPL 15: 3GPP TS 23.502 v15.3.0, “Procedure for 5G System; Stage 2”-   NPL 16: 3GPP TS 37.324 v15.1.0, “NR; Service Data Adaptation    Protocol (SDAP) Specification”-   NPL 17: 3 GPP RP-190728, “New WID: Support of NR Industrial Internet    of Things (IoT)” NPL 18: 3GPP Draft_RAN2_106_Report_v3, “Report of    3GPP TSG RAN WG2 meeting #106” https://www.3gpp.    org/ftp/tsg_ran/WG2_RL2/TSGR2_106/Report/Draft_RAN2_106_Report_v3.    zip-   NPL 19: IEEE 802.1Q-2014—IEEE Standard for Local and metropolitan    area networks—Bridges and Bridged Networks.

SUMMARY OF INVENTION Technical Problem

In the technical studies of NR, a scheme has been examined that expandsexisting NR technologies to the Industrial Internet of Things (IIoT).(NPL 17). The studies include a study of Ethernet header compressiontechnology, which is a technology for reducing the overhead of anEthernet header on data on the assumption that an Ethernet frame istransmitted and/or received by using NR.

A direction of Ethernet header compression has been under study in whichthe Ethernet header compression is implemented by associating Ethernetheader information with an identifier referred to as a contextidentifier and using the context identifier instead of the entireEthernet header information (NPL 18). However, detailed operations of aterminal for efficiently controlling data transmission and/or receptionhave not been under study yet.

An aspect of the present invention has been made in light of theforegoing, and an object of the present invention is to provide aterminal apparatus and a method that can efficiently control datatransmission and/or reception.

Solution to Problem

In order to accomplish the object described above, an aspect of thepresent invention is contrived to provide the following measures.Specifically, a terminal apparatus for communicating with a base stationapparatus is provided, the terminal apparatus including a receiverconfigured to receive an RRC message from the base station apparatus,and a processing unit configured to delete a context identifier of acontext to be released and the context associated with the contextidentifier based on inclusion of the context identifier in the RRCmessage.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a receiver configured to receive an RRC message from the basestation apparatus, and a processing unit configured to, based oninclusion, in the RRC message, of information for configuring a contextmanagement timer, in response to reception of a first service data unitfrom an upper layer, create a first context related to a header includedin the first service data unit and start or restart a first timer forthe first context in a case that the first context related to the headerincluded in the first service data unit is not stored, and start orrestart the first timer and delete the first context based on expiry ofthe first timer in a case that the first context related to the headerincluded in the first service data unit is stored.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a receiver configured to receive an RRC message from the basestation apparatus; and a processing unit configured to, based oninclusion, in the RRC message, of information for configuring a contextmanagement timer, in response to reception of a second protocol dataunit from a lower layer, create a second context related to a headerincluded in the second protocol data unit and start or restart a secondtimer for the second context in a case that the second protocol dataunit includes information indicating that header compression has notbeen performed, and start or restart the second timer and delete thesecond context based on expiry of the second timer in a case that thesecond protocol data unit includes information indicating that headercompression has been performed.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a processing unit configured to receive, from the base stationapparatus, an RRC message including a maximum value of a contextidentifier, and in response to receiving a third service data unit froman upper layer, assign a fourth context identifier associated with oneof stored contexts to a third context related to a header included inthe third service data unit in a case that the third context is notstored and that the number of the stored contexts has reached themaximum value for the context identifiers.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to delete a context identifier of a context to bereleased and the context associated with the context identifier, basedon inclusion of the context identifier in the RRC message.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to, based on inclusion, in the RRC message, ofinformation for configuring a context management timer, in response toreception of a first service data unit from an upper layer, create afirst context related to a header included in the first service dataunit and start or restart a first timer for the first context in a casethat the first context related to the header included in the firstservice data unit is not stored, and start or restart the first timerand delete the first context based on expiry of the first timer in acase that the first context related to the header included in the firstservice data unit is stored.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to, based on inclusion, in the RRC message, ofinformation for configuring a context management timer, in response toreception of a second protocol data unit from a lower layer, create asecond context related to a header included in the second protocol dataunit and start or restart a second timer for the second context in acase that the second protocol data unit includes information indicatingthat header compression has not been performed, and start or restart thesecond timer and delete the second context based on expiry of the secondtimer in a case that the second protocol data unit includes informationindicating that header compression has been performed.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a processing unit configured to transmit an RRC messageincluding a maximum value of a context identifier to the terminalapparatus, and to cause the terminal apparatus to, in response toreceiving a third service data unit from an upper layer, assign a fourthcontext identifier associated with one of stored contexts to a thirdcontext related to a header included in the third service data unit in acase that the third context is not stored and that the number of thestored contexts has reached the maximum value for the contextidentifiers.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, anddeleting a context identifier of a context to be released and thecontext associated with the context identifier based on inclusion of thecontext identifier in the RRC message.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, andbased on inclusion, in the RRC message, of information for configuring acontext management timer, in response to reception of a first servicedata unit from an upper layer, creating a first context related to aheader included in the first service data unit and starting orrestarting a first timer for the first context in a case that the firstcontext related to the header included in the first service data unit isnot stored, and starting or restarting the first timer and deleting thefirst context based on expiry of the first timer in a case that thefirst context related to the header included in the first service dataunit is stored.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, andbased on inclusion, in the RRC message, of information for configuring acontext management timer, in response to reception of a second protocoldata unit from a lower layer, creating a second context related to aheader included in the second protocol data unit and starting orrestarting a second timer for the second context in a case that thesecond protocol data unit includes information indicating that headercompression has not been performed, and starting or restarting thesecond timer and deleting the second context based on expiry of thesecond timer in a case that the second protocol data unit includesinformation indicating that header compression has been performed.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving, from the base station apparatus, an RRC messageincluding a maximum value of a context identifier, and in response toreceiving a third service data unit from an upper layer, assigning afourth context identifier associated with one of stored contexts to athird context related to a header included in the third service dataunit in a case that the third context is not stored and that the numberof the stored contexts has reached the maximum value for the contextidentifiers.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to delete a context identifier of acontext to be released and the context associated with the contextidentifier, based on inclusion of the context identifier in the RRCmessage.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to, based on inclusion, in the RRCmessage, of information for configuring a context management timer, inresponse to reception of a first service data unit from an upper layer,create a first context related to a header included in the first servicedata unit and start or restart a first timer for the first context in acase that the first context related to the header included in the firstservice data unit is not stored, and start or restart the first timerand delete the first context based on expiry of the first timer in acase that the first context related to the header included in the firstservice data unit is stored.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to, based on inclusion, in the RRCmessage, of information for configuring a context management timer, inresponse to reception of a second protocol data unit from a lower layer,create a second context related to a header included in the secondprotocol data unit and start or restart a second timer for the secondcontext in a case that the second protocol data unit includesinformation indicating that header compression has not been performed,and start or restart the second timer and delete the second contextbased on expiry of the second timer in a case that the second protocoldata unit includes information indicating that header compression hasbeen performed.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message including a maximum value of acontext identifier to the terminal apparatus, and causing the terminalapparatus to, in response to receiving a third service data unit from anupper layer, assign a fourth context identifier associated with one ofstored contexts to a third context related to a header included in thethird service data unit in a case that the third context is not storedand that the number of the stored contexts has reached the maximum valuefor the context identifiers.

These comprehensive or specific aspects may be implemented in a system,an apparatus, a method, an integrated circuit, a computer program, or arecording medium, or may be implemented in any combination of systems,apparatuses, methods, integrated circuits, computer programs, andrecording media.

Advantageous Effects of Invention

According to an aspect of the present invention, the terminal apparatuscan implement efficient mobility processing.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a communication system according toeach embodiment of the present invention.

FIG. 2 is a diagram of protocol stacks of UP and CP of a terminalapparatus and a base station apparatus in E-UTRA according to eachembodiment of the present invention.

FIG. 3 is a diagram of protocol stacks of the UP and the CP of theterminal apparatus and the base station apparatus in NR according toeach embodiment of the present invention.

FIG. 4 is a diagram illustrating an example of a flow of a procedure forvarious configurations in an RRC 208 and/or an RRC 308 according to eachembodiment of the present invention.

FIG. 5 is a block diagram illustrating a configuration of a terminalapparatus according to each embodiment of the present invention.

FIG. 6 is a block diagram illustrating a configuration of a base stationapparatus according to each embodiment of the present invention.

FIG. 7 illustrates an example of an ASN.1 notation included in a messagerelated to reconfiguration of RRC connection in NR according to anembodiment of the present invention.

FIG. 8 illustrates an example of an ASN.1 notation included in a messagerelated to reconfiguration of RRC connection in E-UTRA according to anembodiment of the present invention.

FIG. 9 illustrates an example of an ASN.1 notation in which an RRCmessage includes an information element or a field indicatingapplication of Ethernet header compression according to each form of thepresent implementation.

FIG. 10 illustrates an example of an ASN.1 notation in which an RRCmessage includes an information element or a field indicating anEthernet PDU session according to an embodiment of the presentinvention.

FIG. 11 illustrates an example of a processing method of an Ethernetheader compression protocol according to an embodiment of the presentinvention.

FIG. 12 illustrates a first example of a processing method of a UE 122according to an embodiment of the present invention.

FIG. 13 illustrates an example of an ASN.1 notation of informationrelated to a context to be released or deleted which information isincluded in an RRC message according to an embodiment of the presentinvention.

FIG. 14 illustrates a second example of a processing method of the UE122 according to an embodiment of the present invention.

FIG. 15 illustrates an example of an ASN.1 notation in which a PDCPconfiguration information element includes an information element or afield related to a timer for managing context according to an embodimentof the present invention.

FIG. 16 illustrates a third example of a processing method of the UE 122according to an embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

Hereinafter, an embodiment of the present invention will be described indetail with reference to the drawings.

LTE (and LTE-A Pro) and NR may be defined as different Radio AccessTechnologies (RATs). The NR may be defined as a technology included inthe LTE. The LTE may be defined as a technology included in the NR. TheLTE that is connectible to the NR by using Multi Radio Dual connectivitymay be distinguished from the existing LTE. The LTE in which a 5GC isused as a core network may be distinguished from a conventional LTE,where an EPC is used as a core network. The present embodiment may beapplied to the NR, the LTE and other RATs. Terms associated with the LTEand the NR are used in the following description. However, the presentinvention may be applied to other technologies using other terms. In thepresent embodiment, the term “E-UTRA” may be replaced with “LTE,” andthe term “LTE” may be replaced with “E-UTRA.”

FIG. 1 is a schematic diagram of a communication system according toeach embodiment of the present invention.

An E-UTRA 100 is a radio access technology described in NPL 3 or thelike, and includes a cell group (CG) configured in one or multiplefrequency bands. An E-UTRAN Node B (eNB) 102 is a base station apparatusof the E-UTRA 100. An Evolved Packet Core (EPC) 104 is a core networkdescribed in NPL 14 and the like and is designed as a core network forthe E-UTRA 100. An interface 112 is an interface between the eNB 102 andthe EPC 104, where there is a control plane (CP) through which controlsignals are transferred and a user plane (UP) through which user data istransferred.

An NR 106 is a radio access technology described in NPL 9 and the like,and includes a cell group (CG) including one or multiple frequencybands. A gNodeB (gNB) 108 is a base station apparatus in the NR 106. A5GC 110 is a core network described in NPL 2 and the like, and isdesigned as a core network for the NR 106, but may also be used as acore network used for the E-UTRA 100 and including a function to connectto the 5GC 110. Hereinafter, the E-UTRA 100 may include the E-UTRA 100including a function to connect to the 5GC 110.

An interface 114 is an interface between the eNB 102 and the 5GC 110, aninterface 116 is an interface between the gNB 108 and the 5GC 110, aninterface 118 is an interface between the gNB 108 and the EPC 104, aninterface 120 is an interface between the eNB 102 and the gNB 108, andan interface 124 is an interface between the EPC 104 and 5GC 110. Theinterface 114, the interface 116, the interface 118, the interface 120,the interface 124, and the like may be interfaces that allow a CP only,an UP only, or both the CP and UP to pass through. The interface 114,the interface 116, the interface 118, the interface 120, the interface124, and the like may be absent depending on a communication systemprovided by a network operator.

A UE 122 is a terminal apparatus supporting one or all of the E-UTRA 100and the NR 106. As described in one or all of NPL 3 and NPL 9, in a casethat the UE 122 connects to a core network via one or all of the E-UTRA100 and the NR 106, a logical path called a radio bearer (RB) isestablished between the UE 122 and one or all of the E-UTRA 100 and theNR 106. The radio bearer used for the CP is referred to as a SignalingRadio Bearer (SRB), and the radio bearer used for the UP is referred toas a Data Radio Bearer (DRB). Each RB is assigned an RB identity (or anRB ID) and uniquely identified. The RB identity for the SRB is referredto as an SRB identity (or an SRB ID), and the RB identity for the DRB isreferred to as a DRB identity (or a DRB ID).

As described in NPL 3, in a case that a connection destination corenetwork for the UE 122 is an EPC 104, each DRB established between theUE 122 and any or all of the E-UTRA 100 and the NR 106 is uniquelylinked to each Evolved Packet System (EPS) bearer passing through theEPC 104. Each EPS bearer is assigned an EPS bearer identity (or ID), anduniquely identified. Additionally, identical QoS is ensured for datapassing through an identical EPS bearer.

As described in NPL 9, in a case that a connection destination corenetwork of the UE 122 is the 5GC 110, one or multiple DRBs establishedbetween the UE 122 and one or all of the E-UTRA 100 and the NR 106 arefurther linked to one of the Packet Data Unit (PDU) sessions establishedin the 5GC 110. One or multiple QoS flows are present in each PDUsession. Each DRB may be mapped to one or multiple QoS flows present inthe linked PDU session or to none of the QoS flows. Each PDU session isidentified by a PDU session identity (or ID). Additionally, each QoSflow is identified by a QoS flow identity. Identical QoS is ensured fordata passing through an identical QoS flow.

In the EPC 104, any of the PDU sessions and the QoS flows is absent ornone of the PDU sessions and the QoS flows are present. No EPS bearersare present in the 5GC 110. In other words, in a case of being connectedto the EPC 104, the UE 122 has information of the EPS bearers. In a caseof being connected to the 5GC 110, the UE 122 has information of any orall of the PDU sessions and the QoS flows.

In the following description, the eNB 102 and/or the gNB 108 is simplyreferred to as a base station apparatus, and the UE 122 is also simplyreferred to as a terminal apparatus.

FIG. 2 is a diagram of protocol stacks of UP and CP of a terminalapparatus and a base station apparatus in an E-UTRA radio access layeraccording to each embodiment of the present invention.

FIG. 2(A) is a diagram of a protocol stack of the UP used in a case thatthe UE 122 communicates with the eNB 102 in the E-UTRA 100.

A Physical layer (PHY) 200 is a radio physical layer and provides atransmission service to an upper layer by using a physical channel. ThePHY 200 is connected with a Medium Access Control layer (MAC) 202 of anupper layer to be described below via transport channels. Data isexchanged between the MAC 202 and the PHY 200 via the transportchannels. The data is transmitted and/or received via radio physicalchannels between the PHYs of the UE 122 and the eNB 102.

The MAC 202 is a medium access control layer that maps various logicalchannels to various transport channels. The MAC 202 is connected with aradio link control layer (RLC) 204 of an upper layer to be describedbelow via logical channels. The major classifications of the logicalchannel depend on the type of information to be transmitted,specifically, the logical channels are classified into control channelsfor transmitting control information and traffic channels fortransmitting user information. The MAC 202 has a function of controllingthe PHY 200 in order to perform the Discontinuous Reception andTransmission (DRX and DTX), a function of performing a random accessprocedure, a function of reporting transmit power information, afunction of performing HARQ control, and the like (NPL 7).

An RLC 204 is a radio link control layer that segments data receivedfrom a Packet Data Convergence Protocol Layer (PDCP) 206 correspondingto an upper layer and described below, and adjusts the data size suchthat a lower layer can properly transmit the data. Furthermore, the RLC200 also has a function of ensuring Quality of Service (QoS) requiredfor each piece of data. In other words, the RLC 204 has a function ofdata retransmission control or the like (NPL 6).

The PDCP 206 is a packet data convergence protocol layer for efficientlytransmitting IP packets, used as user data, in wireless sections. ThePDCP 206 may include a header compression function to compressunnecessary control information. Additionally, the PDCP 206 may alsoinclude a data ciphering function. (NPL 5).

Note that data processed in the MAC 202, the RLC 204, and the PDCP 206are referred to as a MAC Protocol Data Unit (PDU), an RLC PDU, and aPDCP PDU, respectively. In addition, data delivered from an upper layerto the MAC 202, the RLC 204, and the PDCP 206 or data deliveredtherefrom to an upper layer are respectively referred to as a MACService Data Unit (SDU), an RLC SDU, and a PDCP SDU.

For distinction between PDCP PDUs for data and PDCP PDUs for control,PDCP PDUs may also be referred to as PDCP Data PDUs (PDCP DATA PDUs) andPDCP Control PDUs (PDCP CONTROL PDUs), respectively. For distinctionbetween RLC PDUs for data and RLC PDUs for control, RLC PDUs may also bereferred to as RLC Data PDUs (RLC DATA PDUs) and RLC Control PDUs (RLCCONTROL PDUs), respectively.

FIG. 2(B) is a protocol stack diagram of the CP used by the UE 122 incommunicating with the eNB 102 and a Mobility Management Entity (MME)used as a logical node providing functions such as authentication andmobility management in the E-UTRA 100.

In the protocol stack of the CP, a Radio Resource Control layer (RRC)208 and a non Access Strarum (NAS) 210 are present in addition to thePHY 200, the MAC 202, the RLC 204, and the PDCP 206. The RRC 208 is aradio link control layer that performs processing such as establishment,re-establishment, suspension, resumption, and the like of an RRCconnection, reconfiguration of the RRC connection, for example,configuration of the radio bearer (RB) and the cell group such asestablishment, change, or release, control of logical channels,transport channels, and physical channels, and the like, and furtherperforms configuration of handover and measurement, and the like. TheRBs may be classified into a Signaling Radio Bearer (SRB) and a DataRadio Bearer (DRB), and the SRB may be used as a path for transmittingan RRC message which is control information. The DRB may be used as apath for transmitting the user data. Each RB may be configured betweenthe RRCs 208 of the eNB 102 and the UE 122. In addition, a portion ofthe RB including the RLC 204 and the MAC 202 may be referred to as anRLC bearer (NPL 4). In contrast to the NAS layer carrying signalsbetween the MME and the UE 122, some or all of the layers of the PHY200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 carryingsignals and data between the UE 122 and the eNB 102 may be referred toas Access Strarum (AS) layers.

The functional classification of the MAC 202, the RLC 204, the PDCP 206,and the RRC 208 described above is an example, and some or all of therespective functions may not be implemented. Some or all of thefunctions of each layer may be included in another layer.

Note that an IP layer, a Transmission Control Protocol (TCP) layer, aUser Datagram Protocol (UDP) layer, an application layer, and the likethat are upper layers of the IP layer are upper layers of the PDCP layer(not illustrated). The RRC layer and the non Access Strarum (NAS) layeralso correspond to upper layers of the PDCP layer (not illustrated). Inother words, the PDCP layer is a lower layer of the Transmission ControlProtocol (TCP) layer, the User Datagram Protocol (UDP) layer, and theapplication layer that are upper layers of the RRC layer, the NAS layer,and the IP layer.

FIG. 3 is a diagram of protocol stacks of UP and CP of a terminalapparatus and a base station apparatus in an NR radio access layeraccording to each embodiment of the present invention.

FIG. 3(A) is a diagram of the protocol stack of the UP used by the UE122 in communicating with the gNB 108 in the NR 106.

A physical layer (PHY) 300 is a radio physical layer of the NR and mayprovide a transmission service to an upper layer by using a physicalchannel. The PHY 300 may be connected with the Medium Access Controllayer (MAC) 302 of an upper layer to be described below via thetransport channels. Data may be exchanged between the MAC 302 and thePHY 300 via the transport channels. The data may be transmitted and/orreceived between the PHYs of the UE 122 and the gNB 108 via the radiophysical channel.

Now, the physical channels will be described.

The following physical channels may be used for the radio communicationbetween the terminal apparatus and the base station apparatus.

-   -   Physical Broadcast CHannel (PBCH)    -   Physical Downlink Control CHannel (PDCCH)    -   Physical Downlink Shared CHannel (PDSCH)    -   Physical Uplink Control CHannel (PUCCH)    -   Physical Uplink Shared CHannel (PUSCH)    -   Physical Random Access CHannel (PRACH)

The PBCH is used to broadcast system information required by theterminal apparatuses.

The PBCH may be used to broadcast time indexes (SSB-Indexes) within theperiodicity of synchronization signal blocks (also referred to asSS/PBCH blocks) in NR.

The PDCCH is used to transmit (or carry) downlink control information(DCI) in a case of downlink radio communication (radio communicationfrom the base station apparatus 3 to the terminal apparatus). Here, oneor multiple pieces of DCI (which may be referred to as DCI formats) aredefined for transmission of the downlink control information. In otherwords, a field for the downlink control information is defined as DCIand is mapped to information bits. The PDCCH is transmitted in a PDCCHcandidate. The terminal apparatus monitors a set of PDCCH candidates inthe serving cell. The monitoring means an attempt to decode the PDCCH inaccordance with a certain DCI format. The certain DCI format may be usedfor scheduling of the PUSCH in the serving cell. The PUSCH may be usedfor transmission of user data, transmission of RRC messages, and thelike.

The PUCCH is used to transmit Uplink Control Information (UCI) in a caseof uplink radio communication (radio communication from the terminalapparatus to the base station apparatus). Here, the uplink controlinformation may include Channel State Information (CSI) used to indicatea downlink channel state. The uplink control information may includeScheduling Request (SR) used to request an UL-SCH resource. The uplinkcontrol information may include a Hybrid Automatic Repeat requestACKnowledgement (HARQ-ACK).

The PDSCH may be used to transmit downlink data (Downlink Shared CHannel(DL-SCH)) from the MAC layer. Furthermore, in a case of the downlink,the PDSCH is also used to transmit System Information (SI), a RandomAccess Response (RAR), and the like.

The PUSCH may be used to transmit uplink data (Uplink-Shared CHannel(UL-SCH)) from the MAC layer or to transmit the HARQ-ACK and/or CSIalong with the uplink data. Furthermore, the PSCH may be used totransmit the CSI only or the HARQ-ACK and CSI only. In other words, thePSCH may be used to transmit the UCI only. The PDSCH or the PUSCH may beused to transmit RRC signaling (also referred to as RRC messages) andMAC control elements. In this regard, in the PDSCH, the RRC signalingtransmitted from the base station apparatus may be signaling common tomultiple terminal apparatuses in a cell. The RRC signaling transmittedfrom the base station apparatus may be dedicated signaling for a certainterminal apparatus (also referred to as dedicated signaling). In otherwords, terminal apparatus-specific (UE-specific) information may betransmitted through dedicated signaling to the certain terminalapparatus. Additionally, the PUSCH may be used to transmit UEcapabilities in the uplink.

The PRACH may be used for transmitting a random access preamble. ThePRACH may be used for indicating the initial connection establishmentprocedure, the handover procedure, the connection re-establishmentprocedure, synchronization (timing adjustment) for uplink transmission,and a request for a PUSCH (UL-SCH) resource.

The MAC 302 is a medium access control layer that maps various logicalchannels to various transport channels. The MAC 302 may be connectedwith a Radio Link Control layer (RLC) 304 of is a high layer to bedescribed below via the logical channels. The classification of thelogical channel depends on the type of information to be transmitted,and the logical channels may be classified into the control channels fortransmitting the control information and the traffic channels fortransmitting the user information. The MAC 302 may have a function ofcontrolling the PHY 300 in order to perform the Discontinuous Receptionand Transmission (DRX and DTX), a function of performing the randomaccess procedure, a function of reporting the transmit powerinformation, a function of performing the HARQ control, and the like(NPL 13).

The RLC 304 is a radio link control layer that segments data receivedfrom a Packet Data Convergence Protocol Layer (PDCP) 306 described belowand corresponding to an upper layer and that adjusts the data size suchthat a lower layer can properly transmit the data. Furthermore, the RLC304 may also have a function of ensuring Quality of Service (QoS)required for each piece of data. In other words, the RLC 304 may have afunction of data retransmission control or the like (NPL 12).

The PDCP 306 is a packet data convergence protocol layer thatefficiently transmits user data in wireless sections. The PDCP 306 mayinclude a header compression function to compress unnecessary controlinformation. Additionally, the PDCP 306 may also include a dataciphering function and a data integrity protection function (NPL 11).Note that the user data described above may or may not be an IP packetor an Ethernet frame described in NPL 19 or the like.

A Service Data Adaptation Protocol (SDAP) 310 is a service dataadaptation protocol layer that functions to map the DRB to a downlinkQoS flow transmitted from the 5GC 110 to the terminal apparatus via thebase station apparatus, and to map the DRB to an uplink QoS flowtransmitted from the terminal apparatus to the 5GC 110 via the basestation apparatus, and to store mapping rule information (NPL 16).

Note that the data processed in the MAC 302, the RLC 304, the PDCP 306,and the SDAP 310 are referred to as a MAC Protocol Data Unit (PDU), anRLC PDU, a PDCP PDU, and an SDAP PDU, respectively. Data delivered froman upper layer to the MAC 302, the RLC 304, the PDCP 306, and the SDAP310 or data delivered therefrom to an upper layer are respectivelyreferred to as a MAC Service Data Unit (SDU), an RLC SDU, a PDCP SDU,and an SDAP SDU.

For distinction between SDAP PDUs for data and SDAP PDUs for control,SDAP PDUs may also be referred to as SDAP Data PDUs (SDAP DATA PDUs) andSDAP Control PDUs (SDAP CONTROL PDUs), respectively. For distinctionbetween PDCP PDUs for data and PDCP PDUs for control, PDCP PDUs may alsobe referred to as PDCP Data PDUs (PDCP DATA PDUs) and PDCP Control PDUs(PDCP CONTROL PDUs), respectively. For distinction between RLC PDUs fordata and RLC PDUs for control, RLC PDUs may also be referred to as RLCData PDUs (RLC DATA PDUs) and RLC Control PDUs (RLC CONTROL PDUs),respectively.

FIG. 3(B) is a protocol stack diagram of the CP used by the UE 122 incommunicating with the gNB 108 and an Access and Mobility Managementfunction (AMF) used as a logical node providing functions such asauthentication and mobility management in the NR 106.

In the protocol stack of the CP, a Radio Resource Control layer (RRC)308 and a non Access Strarum (NAS) 312 are present in addition to thePHY 300, the MAC 302, the RLC 304, and the PDCP 306. The RRC 308 is aradio link control layer that performs processing such as establishment,re-establishment, suspension, resumption, and the like of an RRCconnection, reconfiguration of the RRC connection, for example,configuration of the radio bearer (RB) and the cell group such asestablishment, change, or release, control of logical channels,transport channels, and physical channels, and the like, and furtherperforms configuration of handover and measurement, and the like. TheRBs may be classified into a Signaling Radio Bearer (SRB) and a DataRadio Bearer (DRB), and the SRB may be used as a path for transmittingan RRC message which is control information. The DRB may be used as apath for transmitting the user data. Each RB may be configured betweenRRCs 308 of the gNB 108 and the UE 122. In addition, a portion of the RBincluding the RLC 304 and the MAC 302 may be referred to as an RLCbearer (NPL 10). In contrast to the NAS layer carrying signals betweenthe AMF and the UE 122, some or all of the layers of the PHY 300, theMAC 302, the RLC 304, the PDCP 306, the RRC 308, and the SDAP 310carrying signals and data between the UE 122 and the gNB 108 may bereferred to as Access Strarum (AS) layers.

For the SRB, SRB0 to SRB3 described below may be defined. SRB0 may be anSRB used for an RRC message and using a Common Control CHannel (CCCH)corresponding to a logical channel SRB1 may be an SRB for the RRCmessage (which may include a piggybacked NAS message) and for the NASmessage prior to the establishment of SRB2, and the Dedicated ControlCHannel (DCCH) corresponding to a logical channel may be used for allcases. SRB2 may be an SRB for the NAS message, and the DCCHcorresponding to a logical channel may be used for all cases. SRB2 mayhave a lower priority than SRB1. SRB3 may be an SRB for a particular RRCmessage in a case that the UE 122 is configured with EN-DC, NGEN-DC,NR-DC, or the like, and the DCCH corresponding to a logical channel maybe used for all cases. Other SRBs may also be provided for otherapplications.

The functional classification of the MAC 302, the RLC 304, the PDCP 306,the SDAP 310, and the RRC 308 described above is an example, and some orall of the functions may not be implemented. Some or all of thefunctions of each layer may be included in another layer.

Note that an upper layer (not illustrated) of the AS layer may bereferred to as a PDU layer, as described in NPL 2. The PDU layer mayinclude any or all of an IP layer, a Transmission Control Protocol (TCP)layer and a User Datagram Protocol (UDP) layer that are upper layers ofthe IP layer, an Ethernet layer, or other layers. The application layermay be an upper layer of the PDU layer or may be included in the PDUlayer. Note that the PDU layer may be an upper layer with respect to theuser plane of the AS layer. Additionally, the RRC layer and the nonAccess Strarum (NAS) layer may be upper layers of one or all of the SDAPlayer and the PDCP layer (not illustrated). In other words, one or allof the SDAP layer and the PDCP layer are lower layers of any or all ofthe RRC layer, the NAS layer, the IP layer, and the Transmission ControlProtocol (TCP) layer, the User Datagram Protocol (UDP) layer, theEthernet layer, and the application layer that are upper layers of theIP layer.

Note that the Ethernet layer described above may or may not be a layerhaving a function to process the Ethernet frame described in NPL 19 orthe like.

Note that, in each embodiment of the present invention, any or all ofthe following may belong to the application layer: a Session InitiationProtocol (SIP), a Session Description Protocol (SDP), and the like usedfor IMS; a Real-time Transport Protocol (RTP), a Real-time TransportControl Protocol (RTCP), a Hyper Text Transfer Protocol (HTTP), and thelike used for media communication or media communication control; andcodecs of various media and the like.

Note that the RRC layer of the terminal apparatus may perform any or allof establishment, configuration, and control on the physical layer, theMAC layer, the RLC layer, the PDCP layer, and the SDAP layer of theterminal apparatus. The RRC layer of the terminal apparatus mayestablish and/or configure the physical layer, the MAC layer, the RLClayer, the PDCP layer, and the SDAP layer in accordance with the RRCmessage transmitted from the RRC layer of the base station apparatus.The MAC layer, the RLC layer, the PDCP layer, and the SDAP layer mayrespectively be referred to as a MAC sublayer, an RLC sublayer, a PDCPsublayer, and a SDAP sublayer.

Note that an entity may refer to each of the layers belonging to the ASlayer configured for one or all of the terminal apparatus and the basestation apparatus or the function of each layer. Specifically, thephysical layer (PHY layer), the MAC layer, the RLC layer, the PDCPlayer, the SDAP layer, and the RRC layer, on which any or all ofestablishment, configuration, and control is performed for one or all ofthe terminal apparatus and the base station apparatus, or the functionsof the respective layers may be referred to as a physical entity (PHYentity), a MAC entity, an RLC entity, a PDCP entity, an SDAP entity, andan RRC entity. One or multiple entities may be included in each layer.Any or all of establishment, configuration, and control may be performedon the PDCP entity and the RLC entity for each radio bearer. Any or allof establishment, configuration, and control may be performed on the MACentity for each cell group. Any or all of establishment, configuration,and control may be performed on the SDAP entity for each PDU session.

Note that a COUNT value may be used in a case that processing forciphering or integrity protection is performed in the PDCP layer or thePDCP entity. The COUNT value may include a Hyper Frame Number (HFN) anda Sequence Number (SN) added to the header of the PDCP PDU. The sequencenumber may be incremented by one each time a PDCP DATA PDU is generatedby the PDCP layer or PDCP entity on the transmission side. The HFN maybe incremented by one each time the sequence number reaches the maximumvalue.

Note that in each embodiment of the present invention, for a distinctionbetween the E-UTRA protocol and the NR protocol, the MAC 202, the RLC204, the PDCP 206, and the RRC 208 may be respectively referred to as aMAC for E-UTRA or a MAC for LTE, an RLC for E-UTRA or an RLC for LTE, aPDCP for E-UTRA or a PDCP for LTE, and an RRC for E-UTRA or an RRC forLTE. Furthermore, the MAC 302, the RLC 304, the PDCP 306, and the RRC308 may also be referred to as MAC for NR, RLC for NR, RLC for NR, andRRC for NR, respectively. Alternatively, there may be descriptions usinga space such as an E-UTRA PDCP or an LTE PDCP, an NR PDCP, and the like.

As also illustrated in FIG. 1, the eNB 102, the gNB 108, the EPC 104,and the 5GC 110 may be connected to one another via the interface 112,the interface 116, the interface 118, the interface 120, and theinterface 114. Thus, the RRC 208 in FIG. 2 may be replaced with the RRC308 in FIG. 3 to support various communication systems. Furthermore, thePDCP 206 in FIG. 2 may also be replaced with the PDCP 306 in FIG. 3.Furthermore, the RRC 308 in FIG. 3 may include the function of the RRC208 in FIG. 2. Furthermore, the PDCP 306 in FIG. 3 may be the PDCP 206in FIG. 2. In the E-UTRA 100, the NR PDCP may be used as a PDCP even ina case that the UE 122 communicates with the eNB 102.

The state transition of the UE 122 in LTE and NR will now be described.The UE 122 connected to the EPC may be in an RRC_CONNECTED state in acase that an RRC connection has been established. The UE 122 may be inan RRC_INACTIVE state in a case that the RRC connection is suspended (ina case that the UE 122 is connected to the 5GC). In the other cases, theUE 122 may be in an RRC_IDLE state.

Note that the UE 122 connected to the EPC does not have the RRC_INACTIVEstate but that the E-UTRAN may initiate suspension of the RRCconnection. In this case, in response to suspension of the RRCconnection, the UE 122 transitions to the RRC_IDLE state while retainingan AS context of the UE and an identity used for resumption(resumeIdentity). In a case that the UE 122 retains the AS context ofthe UE and that the E-UTRAN permits the RRC connection to be resumed andthat the UE 122 needs to transition from the RRC_IDLE state to theRRC_CONNECTED state, the resumption of the RRC connection suspended maybe initiated by the upper layer (e.g., the NAS layer).

In other words, the definition of the suspension may vary between the UE122 connected to the EPC and the UE 122 connected to the 5GC. All orpart of the procedure for resuming the connection suspended may varybetween a case where the UE 122 is connected to the EPC (the connectionis suspended in the RRC_IDLE state) and a case where the UE 122 isconnected to the 5GC (the connection is suspended in the RRC_INACTIVEstate).

Note that the RRC_CONNECTED state, the RRC_INACTIVE state, and theRRC_IDLE state may be respectively referred to as a connected mode, aninactive mode, and an idle mode.

The AS context of the UE retained by the UE 122 may be informationincluding all or some of a current RRC configuration, a current securitycontext, a PDCP state including a RObust Header Compression (ROHC)state, a Cell Radio Network Temporary Identifier (C-RNTI) used in aPCell of a connection source, a cell identity (cellIdentity), and aphysical cell identity of the PCell of the connection source. Note thatthe AS context of the UE retained by one or all of the eNB 102 and thegNB 108 may include information identical to the information of the AScontext of the UE retained by the UE 122, or may include informationdifferent from the information included in the AS context of the UEretained by the UE 122.

The security context may be information including all or some of aciphering key at the AS level, a Next Hop parameter (NH), a Next HopChaining Counter parameter (NCC) used to derive an access key for thenext hop, an identifier of a ciphering algorithm at a selected AS level,and a counter used for replay protection.

FIG. 4 is a diagram illustrating an example of a flow of a procedure forvarious configurations in the RRC 208 and/or the RRC 308 according toeach embodiment of the present invention. FIG. 4 is an example of a flowin a case that an RRC message is sent from the base station apparatus(eNB 102 and/or gNB 108) to the terminal apparatus (UE 122).

In FIG. 4, the base station apparatus creates an RRC message (stepS400). The creation of the RRC message in the base station apparatus maybe performed in a case that the base station apparatus distributesbroadcast information (System Information (SI)) or paging information,or in a case that the base station apparatus determines a need to causea particular terminal apparatus to perform processing, for example,configuration related to security, reconfiguration of an RRC connection(processing (establishment, change, release, or the like) of the radioline bearer, processing (establishment, addition, change, release, orthe like) of the cell group, measurement configuration, handoverconfiguration, or the like), release of the RRC connected state, or thelike. Additionally, the RRC message may be used for a command forhandover to a different RAT. The RRC message includes information(parameters) for various information notifications and configurations.In specifications related to RRC in NPL 4, NPL 10, or the like, theabove-described parameters are referred to as fields and/or informationelements, and are notated by using a notation method referred to asAbstract Syntax Notation One (ASN.1).

In FIG. 4, the base station apparatus then transmits the RRC messagecreated, to the terminal apparatus (step S402). Then, in a case thatprocessing such as a configuration is necessary in accordance with theRRC message received, the terminal apparatus performs the processing(step S404).

Note that the creation of the RRC message is not limited to the exampledescribed above, and may be performed for other purposes, as describedin NPL 4, NPL 10, and the like.

For example, the RRC message may be used for configuration related toDual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC)described in NPL 8.

The Dual Connectivity (DC) may be a technology for performing datacommunication by using radio resources of both cell groups including amaster cell group (MCG) including master nodes (MNs) and a secondarycell group (SCG) including secondary nodes (SNs), each cell groupincluding two base station apparatuses (nodes). The master node and thesecondary node may be an identical node (identical base stationapparatus). Furthermore, the MR-DC described in NPL 8 may be atechnology in which cells of both Radio Access Technologies (RATs) ofE-UTRA and NR are formed into cell groups for each RAT, which areassigned to the UE, and in which data communication is performed byutilizing radio resources of both MCG and SCG. In the MR-DC, the masternode may be a base station including primary RRC functions related toMR-DC, for example, functions to add a secondary node, to establish,change, and release an RB, to add, change, and release an MCG, and toperform handover and the like, and the secondary base station may be abase station including some RRC functions, for example, functions tochange and release an SCG, and the like.

In the MR-DC described in NPL 8, the RRC corresponding to the masternode side RAT may be used to configure both the MCG and the SCG. Forexample, in E-UTRA-NR Dual Connectivity (EN-DC) corresponding to theMR-DC in which the EPC 104 is used as a core network and the eNB 102(also referred to as an evolved eNB 102) is used as a master node and inNG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC) corresponding to the MR-DCin which the 5GC 110 is used as a core network and the eNB 102 is usedas a master node, an RRC message for E-UTRA described in NPL 4 may betransmitted and received between the eNB 102 and the UE 122. In thiscase, the RRC message may include NR configuration information describedin NPL 10 as well as LTE (E-UTRA) configuration information.Additionally, the RRC message transmitted from the eNB 102 to the UE 122may be transmitted from the eNB 102 to the UE 122 via the gNB 108. Theconfiguration of the present RRC message may be used in E-UTRA/5GC(option 5 described in NPL 17) corresponding to non-MR-DC in which theeNB 102 (evolved eNB) uses the 5GC as a core network.

Additionally, in contrast, in the MR-DC described in NPL 8, in NR-E-UTRADual Connectivity (NE-DC) corresponding to the MR-DC in which the 5GC110 is used as a core network and the gNB 108 is used as a master node,an RRC message for NR described in NPL 10 may be transmitted andreceived between the gNB 108 and the UE 122. In this case, the RRCmessage may include LTE (E-UTRA) configuration information described inNPL 4 as well as NR configuration information. Additionally, the RRCmessage transmitted from the gNB 108 to the UE 122 may be transmittedfrom the gNB 108 to the UE 122 via the eNB 102.

Note that the embodiment is not limited to the case of utilization ofthe MR-DC and that the RRC message for E-UTRA transmitted from the eNB102 to the UE 122 may include an RRC message for NR, whereas or the RRCmessage for NR transmitted from the gNB 108 to the UE 122 may include anRRC message for E-UTRA.

A network configuration in which the eNB 102 is used as a master nodeand the EPC 104 is used as a core network may be referred to asE-UTRA/EPC. Additionally, a network configuration in which the eNB 102is used as a master node and the 5GC 110 is used as a core network maybe referred to as E-UTRA/5GC. In addition, a network configuration inwhich the gNB 108 is used as a master node and the 5GC 110 is used as acore network may be referred to as NR or NR/5GC. Moreover, thisdesignation need not be limited to a case where the DC is configured. inthe case that the DC is not configured, the above-described master nodemay refer to a base station apparatus that communicates with theterminal apparatus.

The UE 122 illustrated in FIG. 5 includes a receiver 500 configured toreceive an RRC message and the like from a base station apparatus, aprocessing unit 502 configured to perform processing in accordance withany or all of pieces of configuration information such as variousinformation elements (IEs), various fields, and various conditionsincluded in the message received, and a transmitter 504 configured totransmit the RRC message and the like to the base station apparatus. Theabove-described base station apparatus may be the eNB 102 or the gNB108. The processing unit 502 may include some or all of the functions ofvarious layers (e.g., the physical layer, the MAC layer, the RLC layer,the PDCP layer, the SDAP layer, the RRC layer, and the NAS layer). Inother words, the processing unit 502 may include some or all of aphysical layer processing unit, a MAC layer processing unit, an RLClayer processing unit, a PDCP layer processing unit, an RRC layerprocessing unit, and an NAS layer processing unit.

FIG. 6 is a block diagram illustrating a configuration of the basestation apparatus according to each embodiment of the present invention.Note that FIG. 6 illustrates only the main components closely related toone aspect of the present invention in order to avoid complexity ofdescription. The above-described base station apparatus may be the eNB102 or the gNB 108.

The base station apparatus illustrated in FIG. 6 includes a transmitter600 configured to transmit an RRC message and the like to the UE 122, aprocessing unit 602 configured to create an RRC message including any orall of pieces of configuration information such as various informationelements (IEs), various fields, and various conditions and to transmitthe RRC message to the UE 122 to cause the processing unit 502 of the UE122 to perform processing, and a receiver 604 configured to receive theRRC message and the like from the UE 122. Furthermore, the processingunit 602 may include some or all of the functions of various layers(e.g., the physical layer, the MAC layer, the RLC layer, the PDCP layer,the RRC layer, and the NAS layer). In other words, the processing unit602 may include some or all of the physical layer processing unit, theMAC layer processing unit, the RLC layer processing unit, the PDCP layerprocessing unit, the SDAP processing unit, the RRC layer processingunit, and the NAS layer processing unit.

FIG. 7 illustrates an example of an ASN.1 notation representing one orall of a field and an information element related to a radio bearerconfiguration included in a message related to reconfiguration of RRCconnection in NR in FIG. 4. FIG. 8 illustrates an example of an ASN.1notation representing one or all of a field and an information elementrelated to a radio bearer configuration included in a message related toreconfiguration of RRC connection in E-UTRA in FIG. 4. In examples ofASN.1, not only in FIGS. 7 and 8, according to an embodiment of thepresent invention, <omitted> and <partly omitted> are not part of theASN.1 notation but other information is omitted. Note that there mayalso be omitted information elements in a part where neither <omitted>nor <partly omitted> is indicated. Note that the examples of ASN.1according to an embodiment of the present invention do not correctlyfollow the ASN.1 notation but represent examples of parameters in amessage related to reconfiguration of RRC connection according to anembodiment of the present invention and that any other designation andany other notation may be used. The examples of ASN.1 according to anembodiment of the present invention correspond to only examples relatedto main information closely associated with an aspect of the presentinvention in order to avoid complicated description. Note that, in anembodiment of the present invention, the parameters notated in ASN.1 mayall be referred to as information elements without distinction betweenfields, information elements, or the like. In an embodiment of thepresent invention, the parameters such as fields and informationelements notated in ASN.1, the parameters being included in the RRCmessage, may also be referred to as information. Note that the messagerelated to reconfiguration of RRC connection may be an RRCreconfiguration message in NR or an RRC connection reconfigurationmessage in E-UTRA.

In FIG. 7, the information element represented by RadioBearerConfig isan information element related to configurations of radio bearers suchas SRBs or DRBs and include PDCP configuration information elements andSDAP configuration information elements to be described later. Aninformation element represented by SRB-ToAddMod and included in theinformation elements represented by RadioBearerConfig may be informationindicating a signaling radio bearer (SRB) configuration, and may also bereferred to as an SRB configuration information element or a signalingradio bearer configuration information element. An information elementrepresented by SRB-ToAddModList may be a list of pieces of informationindicating SRB configurations. An information element represented byDRB-ToAddMod and included in the information elements represented byRadioBearerConfig may be information indicating a data radio bearer(DRB) configuration, and may also be referred to as a DRB configurationinformation element or a data radio bearer configuration informationelement. An information element represented by DRB-ToAddModList may be alist of pieces of information indicating DRB configurations. Note thatany or all of the SRB configurations and the DRB configurations may bereferred to as radio bearer configurations.

An information element included in the SRB configuration informationelements and represented by SRB-Identity is information of SRB identityof an SRB to be added or changed, and may be an identifier that uniquelyidentifies the SRB at each terminal apparatus. This information elementmay be replaced with an SRB identity information element, a radio beareridentity information element, or a signaling radio bearer identityinformation element.

An information element included in the DRB configuration informationelements and represented by DRB-Identity is an information of DRBidentity of a DRB to be added or changed, and may be an identifier thatuniquely identifies the DRB at each terminal apparatus. This informationelement may be replaced with a DRB identity information element, a radiobearer identity information element, or a data radio bearer identityinformation element. In the example illustrated in FIG. 7, the DRBidentity has an integer value ranging from 1 to 32. However, the DRBidentity may take another value. For DC, the DRB identity is uniquewithin the scope of the UE 122.

An information element included in the DRB configuration informationelements and represented by cnAssociation may be an information elementindicating whether the EPC 104 or the 5GC 110 is used as a core network,and may also be referred to as a core network association informationelement. In other words, in a case that the UE 122 is connected to theEPC, the DRB may be associated with an EPS bearer identity informationelement (eps-BearerIdentity) in cnAssociation or with an EPS beareridentity corresponding to the value of the EPS bearer identityinformation element. In a case that the UE 122 is connected to the 5GC110, the DRB may be associated with an SDAP entity configured inaccordance with an SDAP configuration information element (sdap-Config)described below, or a PDU session information element described belowand included in the SDAP configuration information element, or a PDUsession identity corresponding to the value of the PDU sessioninformation element, or a PDU session indicated by the PDU sessioninformation element. In other words, the information represented bycnAssociation may include an EPS bearer identity information element(eps-BearerIdentity) in a case that the EPC 104 is used as a corenetwork, such as in a case of using EN-DC, and may include aninformation element (sdap-Config) indicating an SDAP configuration in acase that the 5GC 110 is used as a core network, in other words, in acase of not using EN-DC.

The information element represented by sdap-Config may be informationrelated to a configuration or reconfiguration of the SDAP entity thatdetermines a mapping method between the QoS flow and the DRB in a casethat the 5GC 110 is used as a core network, and may be replaced with anSDAP configuration information element.

A field or an information element included in the SDAP configurationinformation elements and represented by pdu-session or PDU-SessionID maybe the PDU session identity of a PDU session described in NPL 2 and towhich the QoS flow mapped to the radio bearer corresponding to the valueof the radio bearer identity information element belongs, the radiobearer identity information element being included in the DRBconfiguration information elements including the present SDAPconfiguration information element, and may be replaced with a PDUsession identity information element. The value of the PDU sessionidentity information element may be an integer that is not negative.Additionally, at each of the terminal apparatuses, multiple DRBidentities may correspond to one PDU session identity.

An information element included in the SDAP configuration informationelements and indicated by mappedQoS-FlowsToAdd may be informationindicating a list of QoS flow identity (QFI) information elementsdescribed below of QoS flows to be mapped to or additionally mapped tothe radio bearer corresponding to the value of the radio bearer identityinformation element included in the DRB configuration informationelements including the present SDAP configuration information elements,and may be replaced with an added QoS flow information element. The QoSflow described above may be a QoS flow of a PDU session indicated by thePDU session information element included in the present SDAPconfiguration information elements.

An information element included in the SDAP configuration informationelements and indicated by mappedQoS-FlowsToRelease may be informationindicating a list of QoS flow identity (QFI) information elementsdescribed below of QoS flows from which a mapping relationship is to bereleased and which are included in the QoS flows mapped to the radiobearer corresponding to the value of the radio bearer identityinformation element included in the DRB configuration informationelements including the present SDAP configuration information elements,and may be replaced with a released QoS flow information element. TheQoS flow described above may be a QoS flow of a PDU session indicated bythe PDU session information element included in the present SDAPconfiguration information elements.

An information element indicated by QFI may be a QoS flow identitydescribed in NPL 2 and uniquely identifying a QoS flow, and may bereplaced with a QoS flow identity information element. The value of theQoS flow identity information element may be an integer that is notnegative. The value of the QoS flow identity information element may beunique to the PDU session.

Furthermore, the SDAP configuration information elements may include, inaddition to the above-described information elements, an uplink headerinformation element indicating whether an uplink SDAP header is presentin uplink data transmitted via the configured DRB, a downlink headerinformation element indicating whether a downlink SDAP header is presentin downlink data received via the configured DRB, a default bearerinformation element indicating whether the configured DRB is a defaultradio bearer (default DRB), and the like.

Information elements included in the SRB configuration informationelements and the DRB configuration information elements and representedby pdcp-Config or PDCP-Config may be information elements used toestablish or change the PDCP 306 for the SRB and/or the DRB and relatedto the configuration of an NR PDCP entity, and may be replaced with PDCPconfiguration information elements. The information elements related tothe configuration of the NR PDCP entity include an information elementindicating the size of an uplink sequence number, an information elementindicating the size of a downlink sequence number, an informationelement indicating a profile of header compression (RObust HeaderCompression (RoHC)), a re-ordering timer information element, and thelike.

An information element represented by DRB-ToReleaseList and included inthe information elements represented by RadioBearerConfig may includeinformation indicating one or more DRB identities to be released.

In FIG. 8, an information element represented byradioResourceConfigDedicated may be an information element used forconfiguration, change, release, or the like of the radio bearer. Aninformation element represented by SRB-ToAddMod and included in theinformation elements represented by RadioResourceConfigDedicated may beinformation indicating a signaling radio bearer (SRB) configuration, andmay be replaced with an SRB configuration information element or asignaling radio bearer configuration information element. An informationelement represented by SRB-ToAddModList may be a list of piece ofinformation indicating SRB configurations. An information elementrepresented by DRB-ToAddMod and included in the information elementsrepresented by RadioResourceConfigDedicated may be informationindicating a data radio bearer (DRB) configuration, and may be replacedwith a DRB configuration information element or a data radio bearerconfiguration information element. An information element represented byDRB-ToAddModList may be a list of pieces of information indicating DRBconfigurations. Note that any or all of the SRB configurations and theDRB configurations may be referred to as radio bearer configurations.

An information element included in the SRB configuration informationelements and represented by SRB-Identity is information of SRB identityof an SRB to be added or changed, and may be an identifier that uniquelyidentifies the SRB at each terminal apparatus. This information elementmay be replaced with an SRB identity information element, a radio beareridentity information element, or a signaling radio bearer identityinformation element. An information element represented by SRB-Identityin FIG. 8 may be an information element having a role identical to therole of the information element represented by SRB-Identity in FIG. 7.

An information element included in the DRB configurations andrepresented by DRB-Identity may be information of DRB identity of a DRBto be added or changed and may be a DRB identity uniquely identifying,at each terminal apparatus, the DRB. This information element may bereplaced with a DRB identity information element, a radio beareridentity information element, or a data radio bearer identityinformation element. In the example illustrated in FIG. 8, the DRBIdentity has an integer value ranging from 1 to 32. However, the DRBidentity may take another value. The information element represented byDRB-Identity in FIG. 8 may be an information element having a roleidentical to the role of the information element represented byDRB-Identity in FIG. 7.

An information element included in the DRB configuration informationelements and represented by eps-BearerIdentity may be an EPS beareridentity uniquely identifying an EPS bearer at each terminal apparatus.The information element represented by eps-BearerIdentity may bereferred to as an EPS bearer identity information element. In theexample illustrated in FIG. 8, the EPS bearer Identity has an integervalue ranging from 1 to 15. However, the EPS bearer identity may takeanother value. The information element represented by eps-BearerIdentityin FIG. 8 may be an information element having a role identical to therole of the information element represented by eps-BearerIdentity inFIG. 7. At each terminal apparatus, the EPS bearer identities maycorrespond to the DRB identities on a one-to-one basis.

An information element included in the SRB configuration informationelements and the DRB configuration information elements and representedby pdcp-Config or PDCP-Config may be an information element related tothe configuration of an E-UTRA PDCP entity and used to establish orchange the PDCP 206 for the SRB and/or for the DRB, and may be replacedwith a PDCP configuration information element. The information elementsrelated to the configuration of the E-UTRA PDCP entity may include aninformation element indicating the size of the sequence number, aninformation element indicating the profile of header compression (RObustHeader Compression (RoHC)), re-ordering timer information, and the like.

Additionally, some or all of the information elements illustrated inFIG. 7 or FIG. 8 may be optional. In other words, the informationelements illustrated in FIG. 7 or FIG. 8 may be included in a messagerelated to the reconfiguration of RRC connection depending onrequirements or conditions. In addition, the message related to thereconfiguration of RRC connection may include an information elementmeaning that a full configuration is to be applied, in addition to aninformation element related to the configuration of the radio bearer.The information element meaning that the full configuration is to beapplied may be represented by an information element name such asfullConfig, and true, enable, or the like may be used to indicateapplication of the full configuration.

An information element represented by DRB-ToReleaseList and included inthe information elements represented by RadioResourceConfigDedicated mayinclude information indicating one or more DRB identities to bereleased.

Now, an example of a processing method of an Ethernet header compressionprotocol according to an embodiment of the present invention will bedescribed with reference to FIGS. 9 to 11. Note that the Ethernet headercompression protocol described above may be referred to as Ethernetheader compression processing. The Ethernet header compressionprocessing may be performed based on the inclusion, in the RRC messagetransmitted to the UE 122 from the base station apparatus, of aninformation element or a field indicating application of Ethernet headercompression and/or an information element or a field indicating anEthernet PDU session. In the present example, an example has beendescribed in which the Ethernet header compression is performed in thePDCP entity. However, the Ethernet header compression may be performedby an entity in another layer. The base station apparatus may be the eNB102 or the gNB 108, but the description below uses the gNB 108 to avoidcomplicated description. In an embodiment of the present invention, theEthernet header may be part or all of the communication controlinformation included in the Ethernet frame. In an embodiment of thepresent invention, the Ethernet frame may be an IEEE 802.1 Medium AccessControl (MAC) frame format, which is described in IEEE documents such asNPL 19.

FIG. 9 illustrates an example of an ASN.1 notation in which the RRCmessage transmitted from the gNB 108 to the UE 122 includes aninformation element or a field indicating application of the Ethernetheader compression. FIG. 10 illustrates an example of an ASN.1 notationin which the RRC message transmitted from the gNB 108 to the UE 122includes an information element or a field indicating an Ethernet PDUsession. Note that as in the case of FIGS. 7 and 8, in the examples ofASN.1, <omitted> and <partly omitted> are not part of the ASN.1 notationbut indicate that other information is omitted. Note that there may alsobe omitted information elements in a part where neither <omitted> nor<partly omitted> is indicated. Note that the examples of ASN.1 do notcorrectly follow the ASN.1 notation but represent examples of parametersin the RRC message according to an embodiment of the present inventionand that any other designation and any other notation may be used. Theexamples of ASN.1 correspond to only examples related to maininformation closely associated with an aspect of the present inventionin order to avoid complicated description. Note that the parametersnotated in ASN.1 may all be referred to as information elements withoutdistinction between fields, information elements, or the like. In anembodiment of the present invention, the parameters such as fields andinformation elements notated in ASN.1, the parameters being included inthe RRC message, may also be referred to as information.

FIG. 9 illustrates an example in which the PDCP configurationinformation element in FIG. 7 and/or FIG. 8 includes an informationelement or a field indicating application of the Ethernet headercompression. In FIG. 9, the field or information element indicated bythe designation ethernetHeaderCompression-r16 and included in the PDCPconfiguration information element is a field or information element forconfiguration for the Ethernet header compression protocol. Hereinafter,the field or information element for configuration related to theEthernet header compression protocol may be referred to as an EthernetHeader Compression (EHC) configuration. The Ethernet header compressionconfiguration may be present only in a case that the PDCP entity for theDRB associated with the Ethernet PDU session is established, andotherwise need not be present. The field or information element includedin the Ethernet header compression configuration and indicated by thedesignation notUsed may be a field or an information element indicatingthat the Ethernet header compression is not applied or that the Ethernetheader compression is not configured. The field or information elementincluded in the Ethernet header compression configuration and indicatedby the designation ehc may be information indicating that the Ethernetheader compression is applied or that the Ethernet header compression isconfigured, or may include information required to apply the Ethernetheader compression. The above-described information required to applythe Ethernet header compression may, for example, be the maximum valuefor the context identity or context identifier (CID). The maximum valuefor the context identifier described above may be the maximum value of anon-negative integer or a positive integer that can be used as a contextidentifier, or may be the upper limit of the number of integers that canbe used as context identifiers. In the example in FIG. 9, the fieldindicated by the designation ehc-maxCID indicates the maximum value forthe context identifiers described above. In the notation example in FIG.9, the maximum value for the context identifiers may take an integerfrom 1 to 127, and the default value is specified as 15, but thesevalues need not necessarily be used. The maximum value for the contextidentifiers being ‘0’ or ‘1’ may mean that the Ethernet headercompression is not applied. The configuration may be such that the totalof the maximum values of the context identifiers in all DRBs for the PDUsession should not exceed the maximum number of context identifiers perPDU session or per UE, which number has been sent to the gNB by the UE122 as UE capability. Note that the context identifier may be anidentifier for uniquely identifying the information required to compressand/or decompress the Ethernet header. Also, the above-describedinformation required to compress and/or decompress the Ethernet headermay be part or all of the Ethernet header information. Theabove-described part or all of the Ethernet header information may beinformation to be compressed by the Ethernet header compression whichinformation is included in the Ethernet header information. Theabove-described information required to compress and/or decompress theEthernet header may be referred to as a context. The information may bean Ethernet header compression profile. The information element or fieldindicated by the designation ehc-profiles in FIG. 9 may be theabove-described information element indicating the Ethernet headercompression profile. The Ethernet header compression profile describedabove may indicate an Ethernet header compression method. The Ethernetheader compression method described above may be a method specifyingwhich field of the header is to be compressed. The relationship betweenthe Ethernet header compression profile described above and the Ethernetheader compression method described above may be a relationship suchthat, for example, in a case that three fields A, B, and C are presentin the Ethernet header, profile 1 indicates that only A is compressed,profile 2 indicates that only A and B are compressed, and profile 3indicates that A, B, and C are compressed. The information element orfield indicating profile 1 described above may be indicated by aninformation element or a field indicated by the designationehc-profile0x0001 in FIG. 9. The information elements or fieldsindicating the profile 2 described above may also be indicated byinformation elements or fields indicated by the designationehc-profile0x0002 in FIG. 9. The information elements or fieldsindicating the profile 3 described above may also be indicated byinformation elements or fields indicated by the designationehc-profile0x0003 in FIG. 9. The above-described Ethernet headercompression profile may indicate the type of an Ethernet frame format.The type of the Ethernet frame format may include, for example,Ethernet2, an Ethernet2+802.1Q tag, an Ethernet2+802.1Q tag+802.1Q tag,and the like, which are described in IEEE documents such as NPL 19. TheEthernet header compression profile described above may be informationindicating a combination of some or all of the Ethernet headercompression method described above, the type of the Ethernet frameformat described above, and other information. The UE 122 may configurethe Ethernet header compression based on the inclusion, in the RRCmessage received from the gNB 108, of information indicating that theEthernet header compression described above is performed or that theEthernet header compression is configured. The information required toapply the Ethernet header compression described above may be contextidentifier information available (not illustrated). The contextidentifier information available may be provided as a range such as“from 10 to 20”, or specified as values such as “5, 10, 15, and 20.”

Note that some or all of the fields and information elements in FIG. 9may be separately configured for transmission (uplink) and/or forreception (downlink). In other words, different information elements orfields may be used for uplink and downlink.

FIG. 10 illustrates an example in which the SDAP configurationinformation element in FIG. 7 includes an information element or a fieldindicating an Ethernet PDU session. In FIG. 10, the field or informationelement indicated by the designation ethernetPduSession-r16 may be afield or an information element indicating that a PDU session associatedwith an SDAP entity established and/or configured by the present SDAPconfiguration information element is an Ethernet PDU session or whetherthe PDU session is an Ethernet PDU session. In a case that the field orinformation element indicated by the designation ethernetPduSession-r16is true, this may indicate an Ethernet PDU session. The field orinformation element for configuration related to the Ethernet headercompression protocol in FIG. 9 may be present exclusively in a case thatthe field or information element includes information indicating anEthernet PDU session in FIG. 10. Note that, in a case that the RRCmessage received from the gNB 108 includes the above-describedinformation element or field indicating an Ethernet PDU session, theSDAP entity of the UE 122 may consider the upper layer as the Ethernetlayer, or may deliver, to the Ethernet layer, an SDAP SDU into which anSDAP PDU received from the lower layer is processed.

FIG. 11 illustrates an example of the processing method of the Ethernetheader compression protocol according to an embodiment of the presentinvention. The PDCP entity of the UE 122 checks the Ethernet header ofthe PDCP SDU received from the upper layer, and in a case that theEthernet header information to be compressed is not stored along with acontext identifier as a context, the PDCP entity stores, as a context,the above-described Ethernet header information to be compressed, andassociates the Ethernet header information with the context identifier.The context identifier and context may be associated with each other ona one-to-one basis. The context identifier described above may beincluded in the context described above. Next, the PDCP entity of the UE122 may add, to the PDCP SDU described above, any or all of theassociated context identifier, information indicating that the Ethernetheader has not been compressed or changed, and other information, andsubmit the PDCP SDU to the lower layer. The PDCP entity of the UE 122may check the Ethernet header of the PDCP SDU received from the upperlayer, and in a case that the same information as the Ethernet headerinformation to be compressed is retained together with a contextidentifier as a context, and/or a feedback indicating that the Ethernetheader compression is allowed (or indicating that the context iscorrectly stored) has been received from the corresponding PDCP entityof the gNB 108, delete, from the PDCP SDU described above, the Ethernetheader information to be compressed, add, to the PDCP SDU, any or all ofthe associated context identifier, information indicating that theEthernet header has been compressed or changed, and other information,and submit the PDCP SDU to the lower layer (step S1100).

In a case that the PDCP PDU received from the lower layer explicitly orimplicitly includes information indicating that the Ethernet header hasnot been compressed or changed, the PDCP entity of the UE 122 may use,as a context, the Ethernet header information to be compressed whichinformation is included in the Ethernet header included in the PDCP PDUdescribed above, and store the Ethernet header information inassociation with the context identifier included in the PDCP PDUdescribed above. In response to the storage, a feedback indicating thatthe Ethernet header compression is allowed (or indicating that thecontext is correctly stored) may be transmitted to the correspondingPDCP entity of the gNB 108. In a case that the PDCP PDU received fromthe lower layer explicitly or implicitly includes information indicatingthat the Ethernet header has not been compressed or changed, the PDCPentity of the UE 122 may deliver the PDCP SDU to the upper layer withoutdecompressing the Ethernet header. In a case that the PDCP PDU receivedfrom the lower layer implicitly or explicitly includes informationindicating that the Ethernet header has been compressed or changed, thePDCP entity of the UE 122 may decompress the Ethernet header and deliverthe PDCP SDU to the upper layer in accordance with the stored contextinformation (step S1102).

Note that the above-described Ethernet header information to becompressed may be the total Ethernet header information or part ofEthernet header information. The Ethernet header compression protocoldescribed above is an example, and the procedure described above neednot necessarily be used. Steps S1100 and S1102 have no ordinalrelationship and may be performed as independent steps.

A first example of a processing method of the UE 122 according to anembodiment of the present invention will be described by using FIG. 12.The processing method of the UE 122 according to an embodiment of thepresent invention, illustrated in FIG. 12, generally corresponds toprocessing in which the UE 122 releases or deletes the stored contextbased on the information of the context to be released or deleted, theinformation being transmitted from the gNB 108. For example, in a casethat a QoS flow corresponding to the DRB is released, the gNB 108 maysend, to the UE 122, the information of the context to be released ordeleted to cause the release, from the UE 122, of a contextcorresponding to an Ethernet flow linked to the QoS flow released. Forexample, in a case that no transmission and/or reception of an Ethernetframe corresponding to the context stored in the UE 112 occurs for acertain amount of time, the gNB 108 may send, to the UE 122, informationof the context to be released or deleted to cause the release of thecontext from the UE 122. Note that the processing of the UE 122according to an embodiment of the present invention illustrated in FIG.12 may be performed in a case that the Ethernet header compression isconfigured. Note that the Ethernet flow described above may refer to anEthernet frame in which some or all of a source MAC address and adestination MAC address, and other Ethernet header information are thesame.

In FIG. 12, the processing unit 602 of the gNB 108 creates an RRCmessage for causing the UE 122 to perform processing and transmits themessage to the UE 122 from the transmitter 600 (not illustrated). Thereceiver 500 of the UE 122 receives the RRC message from the gNB 108(step S1200). Note that the RRC message described above may be a messagerelated to reconfiguration of RRC connection or another message. Theabove-described message related to reconfiguration of RRC connection maybe a message named the RRC reconfiguration message described in NPL 10.Note that the UE 122 may receive the above-described message related toreconfiguration of RRC connection from the eNB 102, and the messagerelated to reconfiguration of RRC connection in this case may be amessage named the RRC connection re-establishment message described inNPL 4.

Next, the processing unit 502 of the UE 122 checks whether the RRCmessage described above includes information related to the context tobe released. In a case that the RRC message includes information relatedto the context to be released, then based on the inclusion of theinformation related to the context to be released, the context isreleased (step S1202). Note that the context described above may beassociated with the context identifier for identifying the context. Thecontext identifier and the context described above may be associatedwith each other on a one-to-one basis. The above-described informationrelated to the context to be released may be the context identifierassociated with the corresponding context. The above-describedinformation related to the context to be released may be a list ofcontext identifiers to allow multiple contexts to be released.

Note that the context described above may be the total Ethernet headerinformation in the Ethernet frame. The context identifier describedabove may be an identifier used for the Ethernet header compression. Thecontext described above may be a RoHC context, and the contextidentifier described above may be a context identifier in RoHC.

The above-described information related to the context to be releasedmay be divided into information related to a context to be released foruplink transmission and information related to a context to be releasedfor downlink reception.

The above-described information related to the context to be releasedmay be included in the PDCP configuration information elementillustrated in FIG. 7 and/or FIG. 8. In step S1202, in a case that,based on the inclusion of the information related to the context to bereleased, the context is released, the following procedure may be usedfor the release.

(A) In a case that the value of the radio bearer identity informationelement (or the radio bearer identity field) included in the RRC messagereceived is present as the current configuration for the UE 122, andbased on the inclusion, in the RRC message received, of the informationrelated to the context to be released, the RRC layer of the UE 122notifies the above-described information related to the context to bereleased to the lower layer or the PDCP entity.

(B) In the PDCP entity, based on the upper layer or the RRC layerrequesting the release of the context, the context is released.

Note that, instead of the processing in (A) described above, in a casethat the value of the radio bearer identity information element (or theradio bearer identity field) included in the RRC message received ispresent as the current configuration for the UE 122, and based on theinclusion of the PDCP configuration information element in the RRCmessage received, the RRC layer of the UE 122 may reconfigure the PDCPentity in accordance with the PDCP configuration information elementdescribed above. Instead of the processing in (B) described above, inthe PDCP entity, based on the reception, from the upper layer or the RRClayer, of the context identifier of the context to be released, thecontext may be released. The processing in B described above may beperformed in the Ethernet header compression protocol of the PDCPentity.

Note that the PDCP entity of the UE 122 may receive, from the SDAPentity, the above-described information related to the context to bereleased.

Note that in step S1202, the release may be deletion. The term “release”in step S1102 may be replaced with deletion or equivalent term.

FIG. 13 illustrates an example of an ASN.1 notation of informationrelated to a context to be released or deleted which information isincluded in an RRC message received from the gNB 108 by the UE 122 instep S1200 described above. Note that as in FIGS. 7, 8, 9, and 10, inthe examples of ASN.1, <omitted> and <partly omitted> are not part ofthe ASN.1 notation but indicate that other information is omitted. Notethat there may also be omitted information elements in a part whereneither <omitted> nor <partly omitted> is indicated. Note that theexamples of ASN.1 do not correctly follow the ASN.1 notation butrepresent examples of parameters in the RRC message according to anembodiment of the present invention and that any other designation andany other notation may be used. The examples of ASN.1 correspond to onlyexamples related to main information closely associated with an aspectof the present invention in order to avoid complicated description. Notethat the parameters notated in ASN.1 may all be referred to asinformation elements without distinction between fields, informationelements, or the like. In an embodiment of the present invention, theparameters such as fields and information elements notated in ASN.1, theparameters being included in the RRC message, may also be referred to asinformation.

FIG. 13 illustrates an example in which the PDCP configurationinformation element in FIG. 7 and/or FIG. 8 includes an informationelement or a field related to the context to be released or deleted. InFIG. 13, the field or information element included in the PDCPconfiguration information element and indicated by the designationehc-contextToReleaseList-r16 may be an information element or fieldindicating a list of the context identifiers of contexts to be releasedor deleted. In the example of FIG. 13, the information element or fieldindicated by the designation EHC-CID may be an information element orfield indicating a context identifier. The information element or fieldindicated by the designation ehc-maxCID in FIG. 13 may be the same asthe information element or field indicated by the designation ehc-maxCIDin FIG. 9. The information element or field indicating a contextidentifier may be an integer value from 1 to ehc-maxCID.

Note that some or all of the fields and information elements in FIG. 13may be separately configured for transmission (uplink) and/or forreception (downlink). Different information elements or fields may beused for uplink configuration and for downlink configuration.

A second example of the processing method of the UE 122 according to anembodiment of the present invention will be described by using FIG. 14.In general, in the processing method of the UE 122 according to anembodiment of the present invention, illustrated in FIG. 14, each timethe UE 122 receives a PDCP SDU with the same context information (partor all of the Ethernet header information) from the upper layer, the UE122 may start or restart a context deletion timer, and delete thecorresponding context in response to expiry of the timer. Each time theUE 122 receives the PDCP PDU with the same context identifier from thelower layer, the UE 122 may start or restart the context deletion timer,and delete the context in response to expiry of the timer. The value ofthe context deletion timer may be included in the RRC message receivedfrom the gNB 108. Note that the processing of the UE 122 according to anembodiment of the present invention illustrated in FIG. 14 may beperformed in a case that the Ethernet header compression is configured.

In FIG. 14, the processing unit 602 of the gNB 108 creates an RRCmessage for causing the UE 122 to perform processing and transmits themessage to the UE 122 from the transmitter 600 (not illustrated). TheRRC layer of the UE 122 checks whether the RRC message received from thegNB 108 includes an information element or a field related to a timerfor managing context. The above-described timer for managing context maybe interpreted as a timer used to release or delete the context. In acase that the RRC message includes an information element or a fieldrelated to a timer for managing context, the RRC layer of the UE 122 mayrequest that the PDCP entity of the UE 122 use the timer for managingcontext (step S1400).

Note that in step S1400, in a case that the RRC message received fromthe gNB 108 includes an information element or a field related to thetimer for managing context, the RRC layer of the UE 122 may configure,for the PDCP entity of the UE 122, the timer for managing context.

The PDCP entity of the UE 122 checks the Ethernet header of the PDCP SDUreceived from the upper layer to check whether the Ethernet headerinformation to be compressed is stored as a context. In a case that theEthernet header information to be compressed, the information includedin the Ethernet header of the PDCP SDU described above, is not stored asa context, the Ethernet header information to be compressed may beassociated with the context identifier and stored as a context, and thetimer for managing context may be configured for the stored contextdescribed above or the context identifier described above and started orrestarted. Instead of configuring, for the stored context, theabove-described timer for managing context and starting or restartingthe timer, the timer for managing context may be configured for thecontext identifier with which the stored context is associated, and thetimer may be started or restarted. Note that the above-described timerfor managing context may be configured by the RRC layer or the upperlayer. The above-described timer for managing context need notnecessarily be configured. In a case that the Ethernet headerinformation to be compressed, the information included in the Ethernetheader of the PDCP SDU described above, is stored as a context, the PDCPentity of the UE 122 may start or restart the timer for managingcontext, the timer being configured for the stored context describedabove and/or the context identifier with which the context describedabove is associated, or the timer in operation. In response to expiry ofthe timer for managing context, the timer being configured for thecontext described above or the context identifier with which the contextdescribed above is associated, or the timer in operation, the PDCPentity of UE 122 may release or delete the context described aboveand/or the context identifier with which any context described above isassociated (step S1402).

The PDCP entity of the UE 122 checks whether the PDCP PDU received fromthe lower layer explicitly or implicitly includes information indicatingthat the Ethernet header has not been compressed or changed. In a casethat the PDCP PDU described above explicitly or implicitly includesinformation indicating that the Ethernet header has not been compressedor changed, the Ethernet header information to be compressed whichinformation is included in the Ethernet header included in the PDCP PDUdescribed above may be used as a context and stored in association withthe context identifier included in the PDCP PDU described above, and thetimer for managing context may be configured for the stored contextdescribed above or the context identifier described above and started orrestarted. Instead of configuring, for the stored context, theabove-described timer for managing context and starting or restartingthe timer, the timer for managing context may be configured for thecontext identifier with which the stored context is associated, and thetimer may be started or restarted. Note that the above-described timerfor managing context may be configured by the RRC layer or the upperlayer. The above-described timer for managing context need notnecessarily be configured. In a case that the PDCP PDU described aboveexplicitly or implicitly includes information indicating that theEthernet header has been compressed or changed, the PDCP entity of theUE 122 may start or restart the timer for managing context, the timerbeing configured for the context identifier included in the PDCP PDUdescribed above or the context associated with the context identifierdescribed above, or the timer in operation. In response to expiry of thetimer for managing context, the timer being configured for the contextdescribed above or the context identifier with which the contextdescribed above is associated, or the timer in operation, the PDCPentity of the UE 122 may release or delete the context described aboveand/or the context identifier with which any context described above isassociated (step S1404).

Note that, in step S1404, instead of checking whether the PDCP PDUreceived from the lower layer explicitly or implicitly includesinformation indicating that the Ethernet header has not been compressedor changed, the PDCP entity of the UE 122 may check whether the contextassociated with the context identifier included in the PDCP PDU receivedfrom the lower layer is stored. In a case that the context is not storedthat is associated with the context identifier included in the PDCP PDUdescribed above, the Ethernet header information to be compressed whichinformation is included in the Ethernet header included in the PDCP PDUdescribed above may be used as a context and stored in association withthe context identifier included in the PDCP PDU described above, and thetimer for managing context may be configured for the stored contextdescribed above or the context identifier described above and started orrestarted. In a case that the context is stored that is associated withthe context identifier included in the PDCP PDU described above, thetimer for managing context may be started or restarted which timer isconfigured for the stored context described above and/or the contextidentifier with which the context described above is associated or whichtimer is in operation.

Note that, in step S1402 and/or step S1404, the timer for managingcontext may be managed independently for each context and/or for eachcontext identifier. Specifically, a first timer for managing context maybe separately and independently configured for a first context and/or afirst context identifier, and a second timer for managing context may beseparately and independently configured for a second context and/or asecond context identifier, and the first timer for managing context andthe second timer for managing context may be separately andindependently started or restarted. In response to expiry of theabove-described first timer for managing context, the first contextand/or first context identifier described above may be released ordeleted, and in response to expiry of the above-described second timerfor managing context, the second context and/or second contextidentifier described above may be released or deleted.

Note that in step S1402 and/or step S1404, in a case that the gNB 108configures a new timer value for the timer for managing context, all ofthe timers may be restarted or the new timer value may be configured fora timer configured in response to new storage of a context, with nooperation performed on the timer in operation.

Note that, in an embodiment of the present invention, starting a timermay refer to activating the timer.

Note that the processing in step S1402 and/or step 1404 may be performedbased on the fact that the PDCP entity of the UE 122 is requested to usethe timer for managing context by the RRC layer or the upper layer. Theprocessing in step S1402 and/or step 1404 may be performed based on thefact that the timer for managing context is configured for the PDCPentity of the UE 122 by the RRC layer or the upper layer.

Note that steps S1402 and S1404 have no ordinal relationship and may beperformed as independent steps.

Note that the processing in steps S1402 and S1404 may be performed inconjunction with the processing in steps S1100 and S1102 describedabove.

FIG. 15 illustrates an example of an ASN.1 notation in which the PDCPconfiguration information element in FIG. 7 and/or FIG. 8 includes theinformation element or field related to the timer for managing context.In FIG. 15, the field or information element indicated by thedesignation ehcContextDiscardTimer-16 included in the PDCP configurationinformation element may be an information element or a field related tothe timer for managing context. In the example in FIG. 15, the field orinformation element indicated by the designationehcContextDiscardTimer-16 may be present exclusively during setup. Inthe example in FIG. 15, the field or information element indicated bythe designation ehcContextDiscardTimer-16 may take any value among s1,s2, s3, s5, s7, s10, s15, s20, s40, s50, s60, s80, s100, s120, s150, ands180. The parameters represented by sN (N is a natural number) describedabove may each mean N second(s).

Note that some or all of the fields and information elements in FIG. 15may be separately configured for transmission (uplink) and/or forreception (downlink). Different information elements or fields may beused for uplink configuration and for downlink configuration.

A third example of the processing method of the UE 122 according to anembodiment of the present invention will be described by using FIGS. 9and 16. In general, in the processing method of the UE 122 according toan embodiment of the present invention illustrated in FIG. 16, in a casethat the UE 122 newly stores a context for the PDCP SDU received fromthe upper layer and that no context identifier is available, that is,the number of contexts stored in the UE 122 has reached the maximumvalue for the context identifiers configured by the gNB 108, then the UE122 may assign, to the new context, a context identifier associated withany stored context. In this case, an old context may be overwritten witha new context. In a case that a context associated with a contextidentifier is already stored, the context being included in the PDCP PDUreceived from the lower layer by the UE 122, but that the PDCP PDUdescribed above explicitly or implicitly includes information indicatingthat the Ethernet header has not been compressed or changed, the storedcontext may be overwritten with Ethernet header information to becompressed, the information being included in the Ethernet headerincluded in the PDCP PDU described above.

In FIG. 16, the processing unit 602 of the gNB 108 creates an RRCmessage for causing the UE 122 to perform processing and transmits theRRC message to the UE 122 from the transmitter 600 (not illustrated).The UE 122 is configured with the maximum value for the contextidentifiers by the information element or field indicating the maximumvalue for the context identifiers included in the RRC message receivedfrom the gNB 108. Note that the context identifier described above maybe a field or an information element indicated by the designationehc-maxCID illustrated in FIG. 9. The maximum value for the contextidentifiers may be configured by using different fields or informationelements for the maximum value for uplink context identifiers and forthe maximum value for downlink context identifiers (step S1600).

The PDCP entity of the UE 122 checks the Ethernet header of the PDCP SDUreceived from the upper layer to check whether the Ethernet headerinformation to be compressed is stored as a context. In a case that theEthernet header information to be compressed, the information beingincluded in the Ethernet header of the PDCP SDU described above, is notstored as a context and that the number of contexts currently stored hasreached the maximum value for the context identifiers configured, thenthe PDCP entity of the UE 122 may associate, with a new Ethernet flow,one of the context identifiers associated with the contexts currentlystored, i.e., associate the context identifier with the Ethernet headerinformation to be compressed, the information being included in theEthernet header of the PDCP SDU described above, and may store theinformation as a new context. In this case, the above-described contextassociated with the context identifier may be overwritten with a newcontext. In a case that the Ethernet header information to becompressed, the information being included in the Ethernet header of thePDCP SDU described above, is not stored as a context and that the numberof contexts currently stored has reached the maximum value for thecontext identifiers configured, then the PDCP entity of the UE 122 mayavoid storing the Ethernet header information to be compressed as acontext, the information being included in the Ethernet header, and sendthe information without applying the Ethernet header compression (stepS1602). Note that the Ethernet flow described above may refer to anEthernet frame in which part or all of the Ethernet header informationis the same.

The PDCP entity of the UE 122 checks whether the PDCP PDU received fromthe lower layer explicitly or implicitly includes information indicatingthat the Ethernet header has not been compressed or changed. In a casethat the PDCP PDU described above explicitly or implicitly includesinformation indicating that the Ethernet header has not been compressedor changed and that the value of the context identifier included in thePDCP PDU described above is already associated with the stored context,then the PDCP entity of the UE 122 may overwrite the context associatedwith the context identifier described above with the Ethernet headerinformation to be compressed, the information being included in theEthernet header included in the above-described PDCP PDU received fromthe lower layer (step S1604).

Note that steps S1602 and S1604 have no ordinal relationship and may beperformed as independent steps.

Note that, in steps S1602 and/or S1604 described above, for distinctionbetween the PDCP PDU to which the Ethernet header compression is appliedand the PDCP PDU to which the Ethernet header compression is notapplied, a context identifier with a particular value may be used forthe PDCP PDU to which the Ethernet header compression is not applied.For example, the context identifier being zero may indicate that theEthernet header compression is not applied. The context identifierindicating that the Ethernet header compression is not applied may beconfigured by the gNB 108 through the RRC message. Instead of using theparticular context identifier indicating that the Ethernet headercompression is not applied, information indicating that the Ethernetheader compression is not applied may be added to the PDCP PDU. Theinformation indicating that the Ethernet header compression is notapplied may be added to the PDCP header or to a payload portion of thePDCP PDU.

Note that, in an embodiment of the present invention, the processing insteps S1102, S1404, and S1604 may be performed exclusively on the PDCPPDU to which the Ethernet header compression is applied.

In an embodiment of the present invention, the processing in steps S1100and S1402 may be performed exclusively on the PDCP SDU to which theEthernet header compression is applied.

Note that part or all of the processing in the example of the processingmethod of the Ethernet header compression protocol, the first example ofthe processing method of the UE 122, the second example of theprocessing method of the UE 122, and the third example of the processingmethod of the UE 122 according to an embodiment of the present inventionmay be performed cooperatively.

Note that the Ethernet header information to be compressed according toan embodiment of the present invention may be the total Ethernet headerinformation or part of Ethernet header information.

Note that, in an embodiment of the present invention, the Ethernetheader information to be compressed being stored as a context may referto the Ethernet header information to be compressed being associatedwith a context identifier. In an embodiment of the present invention,the context identifier may be part of the context.

In an embodiment of the present invention, storage of a context may beinterpreted as generation of the context, establishment of the context,or any other term.

In an embodiment of the present invention, the implicit inclusion ofinformation indicating that the Ethernet header has been compressed orchanged may refer to non-inclusion of information indicating that theEthernet header has not been compressed or changed. The implicitinclusion of information indicating that the Ethernet header has notbeen compressed or changed may refer to non-inclusion of informationindicating that the Ethernet header has been compressed or changed.

In the Ethernet header compression processing according to an embodimentof the present invention, the processing on the transmission side may beperformed by a compressor for the Ethernet header compression protocol,and the processing on the reception side may be performed by adecompressor for the Ethernet header compression protocol.

In an embodiment of the present invention, the Ethernet headercompression has been described, but part or all of the processing in anembodiment of the present invention may be applied to another headercompression technology, e.g., RoHC.

In the above description, expressions such as “linked,” “mapped”,“associated,” and the like may be replaced with one another.

Note that in the above description, “A may be interpreted as B” or “Amay be B” may include the meaning that B is interpreted as A or that Bis assumed as A, in addition to the meaning that A is interpreted as Bor that A is assumed as B. In a case that the above description contains“C may be D” and “C may be E,” this means inclusion of “D may be E.” Ina case that the above description contains “F may be G” and “G may beH,” this means inclusion of “F may be H.”

Various aspects in an embodiment of the present invention will bedescribed below.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a receiver configured to receive an RRC message from the basestation apparatus, and a processing unit configured to delete a contextidentifier of a context to be released and the context associated withthe context identifier based on inclusion of the context identifier inthe RRC message. Note that the context identifier is used for theEthernet header compression, and the context is part or all of theEthernet header information.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a receiver configured to receive an RRC message from the basestation apparatus, and a processing unit configured to, based oninclusion, in the RRC message, of information for configuring a contextmanagement timer, in response to reception of a first service data unitfrom an upper layer, create a first context related to a header includedin the first service data unit and start or restart a first timer forthe first context in a case that the first context related to the headerincluded in the first service data unit is not stored, and start orrestart the first timer and delete the first context based on expiry ofthe first timer in a case that the first context related to the headerincluded in the first service data unit is stored.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a receiver configured to receive an RRC message from the basestation apparatus; and a processing unit configured to, based oninclusion, in the RRC message, of information for configuring a contextmanagement timer, in response to reception of a second protocol dataunit from a lower layer, create a second context related to a headerincluded in the second protocol data unit and start or restart a secondtimer for the second context in a case that the second protocol dataunit includes information indicating that header compression has notbeen performed, and start or restart the second timer and delete thesecond context based on expiry of the second timer in a case that thesecond protocol data unit includes information indicating that headercompression has been performed.

An aspect of the present invention provides a terminal apparatus forcommunicating with a base station apparatus, the terminal apparatusincluding a processing unit configured to receive, from the base stationapparatus, an RRC message including a maximum value of a contextidentifier, and in response to receiving a third service data unit froman upper layer, assign a fourth context identifier associated with oneof stored contexts to a third context related to a header included inthe third service data unit in a case that the third context is notstored and that the number of the stored contexts has reached themaximum value for the context identifiers.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to delete a context identifier of a context to bereleased and the context associated with the context identifier, basedon inclusion of the context identifier in the RRC message. Note that thecontext identifier is used for the Ethernet header compression, and thecontext is part or all of the Ethernet header information.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to, based on inclusion, in the RRC message, ofinformation for configuring a context management timer, in response toreception of a first service data unit from an upper layer, create afirst context related to a header included in the first service dataunit and start or restart a first timer for the first context in a casethat the first context related to the header included in the firstservice data unit is not stored, and start or restart the first timerand delete the first context based on expiry of the first timer in acase that the first context related to the header included in the firstservice data unit is stored.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a transmitter configured to transmit an RRC message to theterminal apparatus, and a processing unit configured to cause theterminal apparatus to, based on inclusion, in the RRC message, ofinformation for configuring a context management timer, in response toreception of a second protocol data unit from a lower layer, create asecond context related to a header included in the second protocol dataunit and start or restart a second timer for the second context in acase that the second protocol data unit includes information indicatingthat header compression has not been performed, and start or restart thesecond timer and delete the second context based on expiry of the secondtimer in a case that the second protocol data unit includes informationindicating that header compression has been performed.

An aspect of the present invention provides a base station apparatus forcommunicating with a terminal apparatus, the base station apparatusincluding a processing unit configured to transmit an RRC messageincluding a maximum value of a context identifier to the terminalapparatus, and to cause the terminal apparatus to, in response toreceiving a third service data unit from an upper layer, assign a fourthcontext identifier associated with one of stored contexts to a thirdcontext related to a header included in the third service data unit in acase that the third context is not stored and that the number of thestored contexts has reached the maximum value for the contextidentifiers.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, anddeleting a context identifier of a context to be released and thecontext associated with the context identifier based on inclusion of thecontext identifier in the RRC message. Note that the context identifieris used for the Ethernet header compression, and the context is part orall of the Ethernet header information.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, andbased on inclusion, in the RRC message, of information for configuring acontext management timer, in response to reception of a first servicedata unit from an upper layer, creating a first context related to aheader included in the first service data unit and starting orrestarting a first timer for the first context in a case that the firstcontext related to the header included in the first service data unit isnot stored, and starting or restarting the first timer and deleting thefirst context based on expiry of the first timer in a case that thefirst context related to the header included in the first service dataunit is stored.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving an RRC message from the base station apparatus, andbased on inclusion, in the RRC message, of information for configuring acontext management timer, in response to reception of a second protocoldata unit from a lower layer, creating a second context related to aheader included in the second protocol data unit and starting orrestarting a second timer for the second context in a case that thesecond protocol data unit includes information indicating that headercompression has not been performed, and starting or restarting thesecond timer and deleting the second context based on expiry of thesecond timer in a case that the second protocol data unit includesinformation indicating that header compression has been performed.

An aspect of the present invention provides a method for a terminalapparatus for communicating with a base station apparatus, the methodincluding receiving, from the base station apparatus, an RRC messageincluding a maximum value of a context identifier, and in response toreceiving a third service data unit from an upper layer, assigning afourth context identifier associated with one of stored contexts to athird context related to a header included in the third service dataunit in a case that the third context is not stored and that the numberof the stored contexts has reached the maximum value for the contextidentifiers.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to delete a context identifier of acontext to be released and the context associated with the contextidentifier, based on inclusion of the context identifier in the RRCmessage. Note that the context identifier is used for the Ethernetheader compression, and the context is part or all of the Ethernetheader information.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to, based on inclusion, in the RRCmessage, of information for configuring a context management timer, inresponse to reception of a first service data unit from an upper layer,create a first context related to a header included in the first servicedata unit and start or restart a first timer for the first context in acase that the first context related to the header included in the firstservice data unit is not stored, and start or restart the first timerand delete the first context based on expiry of the first timer in acase that the first context related to the header included in the firstservice data unit is stored.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message to the terminal apparatus, andcausing the terminal apparatus to, based on inclusion, in the RRCmessage, of information for configuring a context management timer, inresponse to reception of a second protocol data unit from a lower layer,create a second context related to a header included in the secondprotocol data unit and start or restart a second timer for the secondcontext in a case that the second protocol data unit includesinformation indicating that header compression has not been performed,and start or restart the second timer and delete the second contextbased on expiry of the second timer in a case that the second protocoldata unit includes information indicating that header compression hasbeen performed.

An aspect of the present invention provides a method for a base stationapparatus for communicating with a terminal apparatus, the methodincluding transmitting an RRC message including a maximum value of acontext identifier to the terminal apparatus, and causing the terminalapparatus to, in response to receiving a third service data unit from anupper layer, assign a fourth context identifier associated with one ofstored contexts to a third context related to a header included in thethird service data unit in a case that the third context is not storedand that the number of the stored contexts has reached the maximum valuefor the context identifiers.

A program running on an apparatus according to an aspect of the presentinvention may serve as a program that controls a Central Processing Unit(CPU) and the like to cause a computer to operate in such a manner as toimplement the functions of the above-described embodiments according tothe aspect of the present invention. Programs or the information handledby the programs are temporarily loaded into a volatile memory such as aRandom Access Memory (RAM) while being processed, or stored in anon-volatile memory such as a flash memory, or a Hard Disk Drive (HDD),and then read, modified, and written by the CPU, as necessary.

Note that the apparatuses in the above-described embodiments may bepartially enabled by a computer. In such a case, a program for realizingsuch control functions may be recorded on a computer-readable recordingmedium to cause a computer system to read the program recorded on therecording medium to perform the program. It is assumed that the“computer system” mentioned here refers to a computer system built intothe apparatuses, and the computer system includes an operating systemand hardware components such as a peripheral device. Furthermore, the“computer-readable recording medium” may be any of a semiconductorrecording medium, an optical recording medium, a magnetic recordingmedium, and the like.

Moreover, the “computer-readable recording medium” may include a mediumthat dynamically retains a program for a short period of time, such as acommunication line that is used to transmit the program over a networksuch as the Internet or over a communication line such as a telephoneline, and may also include a medium that retains a program for a fixedperiod of time, such as a volatile memory within the computer system forfunctioning as a server or a client in such a case. Furthermore, theabove-described program may be configured to realize some of thefunctions described above, and additionally may be configured to realizethe functions described above, in combination with a program alreadyrecorded in the computer system.

Furthermore, each functional block or various characteristics of theapparatuses used in the above-described embodiments may be implementedor performed with an electric circuit, that is, typically an integratedcircuit or multiple integrated circuits. An electric circuit designed toperform the functions described in the present specification may includea general purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), or other programmable logic devices, discrete gatesor transistor logic, discrete hardware components, or a combinationthereof. The general-purpose processor may be a microprocessor, or theprocessor may be a processor of known type, a controller, amicro-controller, or a state machine instead. The general-purposeprocessor or the above-mentioned circuits may include a digital circuit,or may include an analog circuit. Furthermore, in a case that withadvances in semiconductor technology, a circuit integration technologyappears that replaces the present integrated circuits, it is alsopossible to use an integrated circuit based on the technology.

Note that the invention of the present application is not limited to theabove-described embodiments. Although apparatuses have been described asan example in the embodiment, the invention of the present applicationis not limited to these apparatuses, and is applicable to a stationarytype or a non-movable type electronic apparatus installed indoors oroutdoors such as a terminal apparatus or a communication apparatus, forexample, an AV device, a kitchen device, a cleaning or washing machine,an air-conditioning device, office equipment, a vending machine, andother household appliances.

Although, the embodiments of the present invention have been describedin detail above referring to the drawings, the specific configuration isnot limited to the embodiments and includes, for example, design changeswithin the scope not depart from the gist of the present invention.Furthermore, various modifications are possible within the scope of oneaspect of the present invention defined by claims, and embodiments thatare made by suitably combining technical means disclosed according tothe different embodiments are also included in the technical scope ofthe present invention. In addition, a configuration in which components,which are described in the embodiment described above, having similareffects are interchanged is also included in the present invention.

INDUSTRIAL APPLICABILITY

An aspect of the present invention can be utilized, for example, in acommunication system, communication equipment (for example, a cellularphone apparatus, a base station apparatus, a wireless LAN apparatus, ora sensor device), an integrated circuit (for example, a communicationchip), or a program.

REFERENCE SIGNS LIST

-   100 E-UTRA-   102 eNB-   104 EPC-   106 NR-   108 gNB-   110 5GC-   112, 114, 116, 118, 120, 124 Interface-   122 UE-   200, 300 PHY-   202, 302 MAC-   204, 304 RLC-   206, 306 PDCP-   208, 308 RRC-   310 SDAP-   210, 312 NAS-   500, 604 Receiver-   502, 602 Processing unit-   504, 600 Transmitter

1-4. (canceled)
 5. A terminal apparatus for communicating with a basestation apparatus, the terminal apparatus comprising: processingcircuitry configured to add an Ethernet Header Compression (EHC) contextidentifier to data in processing of an EHC protocol; and a transmitterconfigured to transmit, to the base station apparatus, the data to whichthe EHC context identifier is added, wherein in a case that the EHCcontext identifier is a particular value, the EHC context identifierindicates that Ethernet header compression is not applied to an Ethernetheader of the data.
 6. The terminal apparatus according to claim 5,further comprising: a receiver configured to receive, from the basestation apparatus, a Radio Resource Control (RRC) message including anEHC configuration, wherein the processing circuitry is configured toconfigure the EHC protocol in accordance with the EHC configuration. 7.The terminal apparatus according to claim 5, wherein the EHCconfiguration includes a maximum value of EHC context identifiers, andthe processing circuitry is configured to, in a case that the number ofEHC contexts stored reaches the maximum value of the EHC contextidentifiers and that a context corresponding to the Ethernet header ofthe data does not exist in the stored EHC contexts, make the EHC contextidentifier to be added to the data the particular value.
 8. A basestation apparatus for communicating with a terminal apparatus, the basestation apparatus comprising: a receiver configured to receive, from theterminal apparatus, data to which an Ethernet Header Compression (EHC)context identifier is added in processing of an EHC protocol; andprocessing circuitry configured to, in a case that the EHC contextidentifier is a particular value, determine that Ethernet headercompression is not applied to an Ethernet header of the data.
 9. Thebase station apparatus according to claim 8, further comprising: atransmitter configured to transmit, to the terminal apparatus, a RadioResource Control (RRC) message including an EHC configuration, whereinthe EHC configuration is used for configuring the EHC protocol of theterminal apparatus.
 10. The base station apparatus according to claim 8,wherein the EHC configuration includes a maximum value of EHC contextidentifiers, and the terminal apparatus makes the EHC context identifieradded to the data the particular value, in a case that the number of EHCcontexts stored reaches the maximum value of the EHC context identifiersand that a context corresponding to the Ethernet header of the data doesnot exist in the stored EHC contexts.
 11. A method for a base stationapparatus for communicating with a terminal apparatus, the methodcomprising: receiving, from the terminal apparatus, data to which anEthernet Header Compression (EHC) context identifier is added inprocessing of an EHC protocol; and determining that Ethernet headercompression is not applied to an Ethernet header of the data, in a casethat the EHC context identifier is a particular value.